System, method, and computer program for automatically certifying a virtual network function (VNF) for use in a network function virtualization (NFV) based communication network

ABSTRACT

A system, method, and computer program product are provided for automatically certifying a Virtual Network Function (VNF) for use in a Network Function Virtualization based (NFV-based) communication network. In use, an online automated VNF certification system receives information associated with at least one VNF. Further, the online automated VNF certification system performs a first level of certification for the at least one VNF by validating metadata corresponding to the information associated with the at least one VNF. Additionally, the online automated VNF certification system performs a second level of certification for the at least one VNF, including testing deployment based functionality associated with the at least one VNF and validating results of testing the deployment based functionality. Still yet, the online automated VNF certification system performs a third level of certification for the at least one VNF by executing one or more test cases associated with the at least one VNF and validating results of executing the one or more test cases. Moreover, the online automated VNF certification system identifies the at least one VNF as certified as a result of performing the third level of certification for the at least one VNF.

FIELD OF THE INVENTION

The present invention relates to telecommunications and/or datacommunications and, more particularly to network function virtualization(NFV) of telecommunications networks.

BACKGROUND

Network Function Virtualization is a term or a name of a proposedarchitecture of telecom services as published by the EuropeanTelecommunications Standards Institute (ETSI) in a series of documentsavailable from the ETSI website. NFV uses generic hardware platform andsoftware adapted for the generic hardware platform. Thus, NFV creates anetwork much more flexible and dynamic than a legacy communicationnetwork. In NFV-based networks, a Virtual Network Function (VNF)decouples the software implementation of the network function from theinfrastructure resources it runs on by virtualization. A network serviceis based on one or more VNFs and/or Physical Network Functions (PNFs),their interconnections, and chaining definitions. The VNFs can beexecuted on almost any generic hardware processing facility. Therefore,VNFs may be installed, removed, and moved between hardware facilities,much more easily, less costly and thus, more frequently.

The flexibility of the NFV-based network enhances the means availablefor optimizing the network's capacity and performance. However, currenttechniques for verifying and certifying VNFs that are to be used inNFV-based networks are limited. Service development is generallyconstrained by the speed of a Network Engineering create, test, anddebug cycle. This is typically a very manual, document-based, and timeconsuming process.

There is thus a need for addressing these and/or other issues associatedwith the prior art.

SUMMARY

A system, method, and computer program product are provided forautomatically certifying a Virtual Network Function (VNF) for use in aNetwork Function Virtualization based (NFV-based) communication network.In use, an online automated VNF certification system receivesinformation associated with at least one VNF. Further, the onlineautomated VNF certification system performs a first level ofcertification for the at least one VNF by validating metadatacorresponding to the information associated with the at least one VNF.Additionally, the online automated VNF certification system performs asecond level of certification for the at least one VNF, includingtesting deployment based functionality associated with the at least oneVNF and validating results of testing the deployment basedfunctionality. Still yet, the online automated VNF certification systemperforms a third level of certification for the at least one VNF byexecuting one or more test cases associated with the at least one VNFand validating results of executing the one or more test cases.Moreover, the online automated VNF certification system identifies theat least one VNF as certified as a result of performing the third levelof certification for the at least one VNF.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates a method for automatically certifying a VirtualNetwork Function (VNF) for use in a Network Function Virtualizationbased (NFV-based) communication network, in accordance with oneembodiment.

FIG. 1B illustrates a method for automatically validating a VNF for usein an NFV-based communication network, in accordance with oneembodiment.

FIG. 2 illustrates a simplified diagram of a system associated with anNFV-based communication network, in accordance with one embodiment.

FIG. 3 illustrates a simplified block diagram of a hardware unit of anNFV-based network, in accordance with one embodiment.

FIG. 4 illustrates a simplified diagram of an NFV management system, inaccordance with one embodiment.

FIG. 5 illustrates a simplified diagram of a deployed NFV-based network,in accordance with one embodiment.

FIG. 6 illustrates a system flow diagram for automatically certifying aVNF for use in an NFV-based communication network, in accordance withone embodiment.

FIG. 7 illustrates a system flow diagram for automatically certifying aVNF for use in an NFV-based communication network, in accordance withone embodiment.

FIG. 8 illustrates a network architecture, in accordance with onepossible embodiment.

FIG. 9 illustrates an exemplary system, in accordance with oneembodiment.

DETAILED DESCRIPTION

FIG. 1A illustrates a method 100 for automatically certifying a VirtualNetwork Function (VNF) for use in a Network Function Virtualizationbased (NFV-based) communication network, in accordance with oneembodiment.

In use, an online automated VNF certification system receivesinformation associated with at least one VNF. See operation 102. Theinformation may be received from a vendor of the VNF. For example, theinformation associated with the VNF may include responses to aquestionnaire provided to a vendor.

The information may include any information associated with the VNF. Forexample, the information associated with the VNF may include a VNF imageassociated with the VNF. As another example, the information associatedwith the VNF may include one or more deployment scripts associated withthe VNF. Of course, the information may include any information in theVNF package (e.g. as mandated by the European TelecommunicationsStandards Institute, etc.). For example, the information would likelyinclude a VNF descriptor, as mandated by ETSI. The information may beassociated with one or more VNFs (e.g. a chain of VNFs, etc.).

In one embodiment, the information associated with the VNF may bereceived via at least one user interface associated with the onlineautomated VNF certification system. In the context of the presentdescription, an online automated VNF certification system refers to anysystem capable of performing certification, verification, and/or testingassociated with VNFs. In various embodiments, the online automated VNFcertification system may include one or more processors, memory,servers, databases, and various computer programs/logic, etc.

In one embodiment, the online automated VNF certification system may beaccessed over one or more networks by vendors, customers, VNF designersand/or VNF testers, etc. In one embodiment, the online automated VNFcertification system may include and/or be associated with a servicedesign and creation (SD&C) onboarding user interface.

As shown further in FIG. 1, the online automated VNF certificationsystem performs a first level of certification for the at least one VNFby validating metadata corresponding to the information associated withthe at least one VNF. See operation 104. In this case, performing thefirst level of certification for the VNF may include validating a formatand structure associated with the VNF image, which was provided with theinformation.

For example, the online automated VNF certification system may expectthe format and/or structure of the information to arrive according to anestablished standard (e.g. in a VNF package as mandated by the EuropeanTelecommunications Standards Institute, etc.). Thus, at least a portionof the first level of certification may include verifying that theinformation received conforms to these requirements. As another example,performing the first level of certification for the VNF may includevalidating VNF descriptor integrity associated with the VNF image.

If the first level of certification fails, various remedies may beavailable. For example, in one embodiment, the online automated VNFcertification system may send a query to the supplier of the VNFinformation (e.g. the vendor, etc.) for additional information and/orinformation in the correct format. As another example, the onlineautomated VNF certification system may automatically reconfigure the VNFinformation to conform to a standard format/structure. As anotherexample, the online automated VNF certification system may alert a user(e.g. a VNF designer, etc.) that the first level of certification hasfailed (e.g. utilizing a user interface, an alert, etc.).

If the first level of certification passes, the VNF may be identified aspassing the first level of certification (e.g. in a database associatedwith the online automated VNF certification system, etc.). In oneembodiment, the VNF may be required to pass the first layer ofcertification before proceeding with the certification process.

With further reference to FIG. 1, the online automated VNF certificationsystem performs a second level of certification for the at least oneVNF, including testing deployment based functionality associated withthe at least one VNF and validating results of testing the deploymentbased functionality. See operation 106. Testing the deployment basedfunctionality may include testing a variety of artifacts associated withthe deployment of the VNF. For example, the second level ofcertification for the VNF may include testing artifact productionassociated with the VNF. As another example, the second level ofcertification for the VNF may include testing software imagedistribution associated with the at least one VNF. As yet anotherexample, the second level of certification for the VNF may includetesting a policy configuration associated with the VNF.

In one embodiment, the VNF may be configured and or modelled prior toperforming the second layer of certification. In this case, the onlineautomated VNF certification system may automatically perform theconfiguration or receive the VNF that was configured/modeled based onthe information associated with the VNF after performing the first levelof certification for the VNF. As one option, a service design andcreation onboarding user interface associated with the online automatedVNF certification system may be utilized to model the VNF prior toperforming the second level of certification. Additionally, the servicedesign and creation onboarding user interface may be utilized toinstantiate the VNF prior to performing the second level ofcertification.

If the second level of certification fails, various remedies may beavailable. For example, in one embodiment, the online automated VNFcertification system may report the failure to a VNF developer and/ortester. As another example, the online automated VNF certificationsystem may automatically attempt to remedy the failure.

If the second level of certification passes, the VNF may be identifiedas passing the second level of certification (e.g. in a databaseassociated with the online automated VNF certification system, etc.). Inone embodiment, the VNF may be required to pass the second layer ofcertification before proceeding with the certification process.

Still yet, the online automated VNF certification system performs athird level of certification for the at least one VNF by executing oneor more test cases associated with the at least one VNF and validatingresults of executing the one or more test cases. See operation 108. Thetest cases may be provided by a vendor and/or be provided by a VNFdesigner and/or VNF tester.

The test cases may be configured for testing any type of functionalityassociated with the VNF. For example, the third level of certificationfor the VNF may include a configuration verification for the VNF. Asanother example, the third level of certification for the VNF mayinclude life cycle management and monitoring associated with the VNF.Additionally, the third level of certification for the VNF may include afunctional certification for the VNF. As another example, the thirdlevel of certification for the VNF may include a basic performanceindication for the VNF.

If the third level of certification fails, various remedies may beavailable. For example, in one embodiment, the online automated VNFcertification system may report the failure to a VNF developer and/ortester. As another example, the online automated VNF certificationsystem may automatically attempt to remedy the failure.

If the third level of certification passes, the VNF may be identified aspassing the third level of certification (e.g. in a database associatedwith the online automated VNF certification system, etc.). Further, theonline automated VNF certification system may identify (e.g. mark,label, document, etc.) the at least one VNF as certified as a result ofperforming the third level of certification for the at least one VNF.See operation 110. In this case, identifying the VNF as certified mayindicate that the VNF is authorized to be utilized in an NFV-basednetwork. Additionally, identifying the VNF as certified may be utilizedto recommend the VNF to customers, etc.

Still yet, in one embodiment, the online automated VNF certificationsystem may perform a fourth level of certification for the VNF,including testing at least one environment specific attribute associatedwith the VNF. The environment specific attribute may be associated witha specific VNF customer and/or NFV environment, etc. In this case, theonline automated VNF certification system may identify the VNF ascertified as a result of performing the fourth level of certificationfor the VNF.

It should be noted that, although the method 100 is described in termsof layers of certification, in various embodiments, aspects of thevarious certifications may be combined into one or more layers.

In one embodiment, in order to provide the pre-procurement of acandidate VNF product for a service provider, as part of thecertification process, the VNF certification system may rely on a listof non-functional key performance indicators (KPIs) that validate theability of at least one VNF to be deployed on an NFV Infrastructure(NFV-I) and orchestrated by the NFV Orchestrator (NFV-O) and VNF-Manager(VNF-M) as specified in the ETSI NFV standardization.

In this case, the KPIs may be based on agreed non-functionalcapabilities validating predefined “Cloud-native” parameters. As anexample, the KPIs used for verification may be associated withmicro-service design, where the VNF components (VNF-Cs) are standard andreusable (e.g. such as a Load Balancer VNF-C, etc.). As another example,the KPIs used for verification may be associated with VNF design,allowing VNF flexible use within a service provider network serviceincluding events and KPIs to provide multiple options for SP deploymentflavors. As another example, the KPIs used for verification may beindependent of a specific NFV-I type and may be deployed on multipleNFV-Is (e.g. Open Stack, VMware, Azure, etc.).

As another example, the KPIs used for verification may be associatedwith resiliency, where the VNF includes a built-in high-availabilitymechanism such as multiple functions arranged in a highly-availablecluster. As yet another example, the KPIs used for verification may beassociated with granular scalability. Additionally, the KPIs used forverification may be associated with clear and flexible license models.As another example, the KPIs used for verification may be associatedwith security features. Still yet, the KPIs used for verification may beassociated with leveraging acceleration ability (e.g. as much aspossible, etc.).

Of course, the KPIs may be associated with any combination of theseparameters. In other words, the verification system may utilize any ofthese non-functional KPIs or associated information to verify one ormore VNFs.

In one embodiment, this certification may be part of the third level ofcertification for the VNF. Of course, this certification may beviewed/implemented as a separate certification/validation process.

FIG. 1B illustrates a method 120 for automatically validating a VNF foruse in an NFV-based communication network, in accordance with oneembodiment.

In operation, the VNF certification system may identify at least one VNFto be validated (e.g. one VNF, a chain of VNFs, etc.). See operation122.

The VNF certification system then identifies criteria associated withone or more KPIs to examine. See operation 124. The VNF certificationsystem analyzes the VNF based on the criteria and determines whether tovalidate the VNF based on the analysis. See operations 126 and 128. Thecriteria associated with the KPIs may include any parameter and/ormeasurement associated with a KPI.

If the validation of method 120 fails, various remedies may beavailable. For example, in one embodiment, the online automated VNFcertification system may report the failure to a VNF developer and/ortester. As another example, the online automated VNF certificationsystem may automatically attempt to remedy the failure.

If the validation of method 120 passes, the VNF may be identified aspassing the validation (e.g. in a database associated with the onlineautomated VNF certification system, etc.). Further, the online automatedVNF certification system may identify (e.g. mark, label, document, etc.)the VNF as certified as a result of performing this certification forthe VNF. In this case, identifying the VNF as certified may indicatethat the VNF is authorized to be utilized in an NFV-based network.Additionally, identifying the VNF as certified may be utilized torecommend the VNF to customers, etc.

In the context of the present description, the terms “network” and“communication network” refer to the hardware and software connectingone or more communication elements including wireline networks, wirelessnetworks, and/or combinations thereof.

The terms “network function virtualization” (NFV) and virtual networkfunction (VNF) are described in a series of documents published by theEuropean Telecommunications Standards Institute (ETSI) and availablefrom the ETSI website. The term “virtual network function or feature”(VNF) refers to a particular implementation of a function, a feature, ora service provided by the network, internally within the network, orexternally to a customer, subscriber, end-user, a terminal or a server.A VNF may include the software program implementation of the function orfeature or service. The term VNF instance (VNF-I) refers to a particularprocess or task executing the VNF program by a particular virtualmachine or processor or computing facility and/or used by a particularcustomer (or subscriber, end-user, terminal or server, etc.).

The term “service” refers to any type of use (such as a use case) that aNFV-based communication network may offer or provide to one or morecommunication elements. A service may include switching data or contentbetween any number of elements, providing content from a server to acommunication element or between servers, securing and protectingcommunication and content, processing content provided by the customeror by a third party, providing backup and redundancy, etc. A service maybe using partial functionality of a VNF or may include one or more VNFsand/or one or more VNF instances forming a service sub-network (orinterconnection model). In the context of the present description, theterm “chain” may refer to such service sub-network, such as a particularplurality of VNFs and/or VNF instances associated with a particularservice type or a service instance.

The term “deployment”, when referring to hardware elements, includingprocessing elements, memory elements, storage elements, connectivity(communication) elements, etc., refer to the configuration or topologyof these hardware elements creating the NFV-based network. The term“deployment”, when referring to software elements, such a VNFs and VNFinstances, refers to the association between such software elements andhardware elements.

The term “deployment optimizations” refers to association of softwareand hardware elements in a manner that satisfies a particular set ofrequirements and/or rules, such as load-related and performance-relatedrequirements, or a manner that makes a better use of a particularhardware deployment, such as by reducing operational cost.

The terms “service deployment optimization”, or “service optimization”or “chain optimization” refer to optimizing the deployment of a servicechain, i.e., optimizing the deployment of one or more VNF instancesmaking a particular service. The terms chain optimization and serviceoptimization may thus be used interchangeably.

The term “session” refers to a communication connection between two ormore entities that persists for a period of time during which data maybe exchanged there between. A session may be implemented and managed bya session layer in the corresponding network protocol. The term sessionmay include a network session and a logical session. The network sessionmay be associated with the devices used to communicate, while thelogical session may be associated with the communicating parties (users)and may persist regardless of the communication means that the partiesare using.

The term “service continuity” includes and applies to the terms “sessioncontinuity” and “streaming continuity”. Streaming refers to streamingmedia, session or service, such as sound (including voice), video,multimedia, animation, etc. The term service usually applies to a groupof VNFs (or the functionality provided by the group of VNFs) but mayalso apply to a single VNF (or the functionality provided by the VNF).The term “continuity” indicates that the session or the service is notinterrupted, or that an interruption is short enough that a user is notaware of such interruption, or that the interruption does not cause anyloss of data, or that the loss is handled in acceptable manner (e.g. afew packets of speech lost, but the conversation can continue, etc.).

The term “availability” or “service availability” refers to a level ofthe service, or a characteristic of the service, in which the serviceprovider should provide the service, albeit possible hardware orsoftware faults. For example, the service provider may obligate to thecustomer to provide a particular level of processing power,communication features such as bandwidth, latency, and jitter, databaseconsistency, etc. Such level or characteristic of the service should beavailable to the customer even when a hardware component or a softwarecomponent providing the service do not function properly. Providingavailability may therefore require additional resources such as backupresources and/or mirroring. Hence “availability” may also refer to theterms “fault recovery” and “redundancy”.

The term “fault recovery” refers to the process of recovering one ormore of the network's services, functions, and features after a fault,whether caused by a hardware malfunction, a system crash, a software bugor a security breech or fault. A hardware malfunction includes, but isnot limited to, any type of inadequate performance associated with, forexample, power supply, processing units, memory, storage, transmissionline, etc. The term “fault recovery” also applies to recovering thefunctionality of one or more VNFs or VNF instances with respect to anyof the above. The terms security breech or security fault may be usedinterchangeably.

The term “redundancy” refers to any type of component of the networkthat is fully or partly duplicated, provided in standby mode, orotherwise available, to replace another component of the network whenthat other component stops functioning properly or otherwise indicatessome kind of fault. Redundancy may apply, but is not limited to,hardware, software, data and/or content.

More illustrative information will now be set forth regarding variousoptional architectures and uses in which the foregoing method may or maynot be implemented, per the desires of the user. It should be stronglynoted that the following information is set forth for illustrativepurposes and should not be construed as limiting in any manner. Any ofthe following features may be optionally incorporated with or withoutthe exclusion of other features described.

The principles and operation of a system, method, and computer programproduct for automatically certifying a VNF for use in an NFV-basedcommunication network according to various embodiments may be furtherunderstood with reference to the following drawings and accompanyingdescription. For example, FIG. 2, etc. illustrates how and where acertified VNF may be deployed in an NFV-based communication network.

FIG. 2 illustrates a simplified diagram of a system 200 associated withan NFV-based communication network 210, in accordance with oneembodiment. As an option, the system 200 may be implemented in thecontext of the details of FIG. 1. Of course, however, system 200 may beimplemented in the context of any desired environment. Further, theaforementioned definitions may equally apply to the description below.

As shown in FIG. 2, at least one NFV-based network 210 is provided. TheNFV-based communication network 210 includes an NFV management system2111, and an NFV-orchestration (NFV-O) module 212, according to oneembodiment.

In the context of the present network architecture, the NFV-basednetwork 210 may take any form including, but not limited to atelecommunications network, a local area network (LAN), a wirelessnetwork, a wide area network (WAN) such as the Internet, peer-to-peernetwork, cable network, etc. While only one network is shown, it shouldbe understood that two or more similar or different NFV-based networks210 may be provided.

The NFV-based network 210 may include one or more computation facilities214, each including one or more hardware units and being interconnectedby communication links to form the NFV-based network 210. At least oneof the computation facilities 214 may include the NFV management system211. The NFV management system 211 may include the NFV-O module 212.

The NFV-O module 212 may be executed by one or more processors, orservers, such as computation facilities 214, of the NFV-based network210. The NFV-O module 212 may be executed as an NFV-O instance orcomponent. The NFV-O module 212 may therefore include a plurality ofNFV-O instances or components as will be further explained below.

In one embodiment, the NFV-based network 210 may even have a pluralityof any of the NFV management systems 211 and/or the NFV-O modules 212.

A plurality of devices 215 are communicatively coupled to the NFV-basednetwork 210. For example, a server computer 216 and a computer orterminal 217 may be coupled to the NFV-based network 210 forcommunication purposes. Such end-user computer or terminal 217 mayinclude a desktop computer, a lap-top computer, a tablet computer,and/or any other type of logic or data processing device. Still yet,various other devices may be coupled to the NFV-based network 210including a personal digital assistant (PDA) device 218, a mobile phonedevice 219, a television 220 (e.g. cable, aerial, mobile, or satellitetelevision, etc.)2, etc. These devices 215 may be owned and/or operatedby end-users, subscribers and/or customers of the NFV-based network 210.Others of the devices 215, such as administration station 221, may beowned and/or operated by the operator of the NFV-based network 210.

A network administrator 222 may supervise at least some aspects of theoperation of the NFV-based network 210 by controlling an NFVinfrastructure including the NFV management system 211 and the NFV-O212.

FIG. 3 illustrates a simplified block diagram 300 of a hardware unit 323of an NFV-based network, in accordance with one embodiment. As anoption, the block diagram 300 may be viewed in the context of thedetails of the previous Figures. Of course, however, block diagram 300may be viewed in the context of any desired environment. Further, theaforementioned definitions may equally apply to the description below.

In one embodiment, the hardware unit 323 may represent a computingfacility 214 of FIG. 2, or a part of a computing facility 214. Thehardware unit 323 may include a computing machine. The term computingmachine relates to any type or combination of computing devices, orcomputing-related units, including, but not limited to, a processingdevice, a memory device, a storage device, and/or a communicationdevice.

The hardware unit 323 may therefore be a network server, and thecomputing facility 214 may be a plurality of network servers, or adata-center, including cloud-based infrastructure. As an option, thehardware unit 323 may be implemented in the context of any of thedevices of the NFV-based network 210 of FIG. 2 and/or FIG. 5 and in anydesired communication environment.

Each hardware unit 323 (or computing machine, computing device,computing-related unit, and/or hardware component, etc.), including eachcommunication link between such hardware units, may be associated withone or more performance type and a respective performance rating orvalue, where the hardware unit and/or communication link is operative toprovide the performance value. Performance types are, for example,processing power, cash memory capacity, regular memory capacity (e.g.RAM, dynamic, or volatile memory, etc.), non-volatile memory (e.g. suchas flash memory, etc.) capacity, storage capacity, power, cooling,bandwidth, bitrate, latency, jitter, bit error rate, and packet loss,etc. Virtual machines may run on top of the hardware unit 323 and a VNFmay be run on one or more of such virtual machines.

The hardware unit 323 may be operative to provide computinginfrastructure and resources for any type and/or instance of softwarecomponent executed within the NFV-based network 210 of FIG. 2. In thisregard, the hardware unit 323 may be operative to process any of theprocesses described herein, including but not limited to, anyNFV-related software component and/or process. The hardware unit 323 isoperative to process virtual network functions (VNFs), VNF instances,network function virtualization orchestration (NFV-O) software, modulesand functions, data center management software, and/or cloud managementsystems (CMS), etc.

In various embodiments, the hardware unit 323 may include at least oneprocessor unit 324, one or more memory units 325 (e.g. random accessmemory (RAM), a non-volatile memory such as a Flash memory, etc.), oneor more storage units 326 (e.g. including a hard disk drive and/or aremovable storage drive, representing a floppy disk drive, a magnetictape drive, a compact disk drive, etc.), one or more communication units327, one or more graphic processors 328 and displays 329, and one ormore communication buses 330 connecting the various units/devices.

The hardware unit 323 may also include one or more computer programs331, or computer control logic algorithms, which may be stored in any ofthe memory units 325 and/or storage units 326. Such computer programs,when executed, enable the hardware unit 323 to perform various functions(e.g. as set forth in the context of FIG. 1, etc.). The memory units 325and/or the storage units 326 and/or any other storage are possibleexamples of tangible computer-readable media.

It is appreciated that computer program 331 may include any of the NFVmanagement system 211 and/or the NFV-O 212 of FIG. 2.

FIG. 4 illustrates a simplified diagram of an NFV management system 411,in accordance with one embodiment. As an option, the NFV managementsystem 411 may be implemented in the context of the details of theprevious Figures. For example, in one embodiment, the NFV managementsystem 411 may represent the NFV management system 211 of FIG. 2. Ofcourse, however, the NFV management system 411 may be implemented in thecontext of any desired environment. Further, the aforementioneddefinitions may equally apply to the description below.

In one embodiment, the NFV management system 411 may include an NFV-Omodule 412. The NFV management system 411 may include one or more NFV-Omodules 412. In various embodiments, each of the NFV-O modules 412 mayinclude orchestration and workflow management 432 that is responsiblefor managing (i.e. orchestrating) and executing all NFV-O processes,including inbound and/or outbound communication and interfaces.

The NFV management system 411 may include a deployment optimizationmodule 433 that enables a user to devise automatic mechanisms fornetwork optimizations. The deployment optimization module 433 mayoperate these mechanisms automatically and continuously to optimize thedistribution of VNFs 450 and their VNF instances in real-time (ornear-real-time) by migrating VNFs 450 and VNF instances (e.g. VNFinstances 551 of FIG. 5, etc.) between hardware units (e.g. hardwareunits 551 of FIG. 5, etc.).

The NFV management system 411 may also include a chain optimizationmodule 434. The chain optimization module 434 may be a part ofdeployment optimization module 433 and may enable a user to deviseautomatic mechanisms for optimizing the deployment of chains or groupsof VNFs 450 and VNF instances. A service provided by an NFV-basednetwork is typically made of a particular chain or group of particularVNFs 450 and their respective VNF instances. The chain optimizationmodule 434 optimizes the deployment of chains or groups of servicesbetween hardware units according to the requirements and specificationsassociated with and/or adapted to the particular service, or chain, or agroup.

The chain optimization module 434 may operate these mechanismsautomatically and continuously to optimize in real-time the operation ofchains or groups of the VNFs 450 and their VNF instances by re-planningtheir distribution among hardware units and optionally also by migratingthe VNFs 450 and associated VNF instances between hardware units.

The NFV management system 411 may also include a service fulfillmentmodule 435 that manages service and resource (e.g. VNF) instancelifecycle activities as part of the process and orchestrationactivities. This may include on boarding, initiation (e.g.instantiation), installation and configuration, scaling, termination,software update (e.g. of a running VNF, etc.), test environment, and/orrollback procedure. Additionally, the service fulfillment module 435 mayalso provide decomposition of an order to multiple network services, andthe activation of such network service as a single VNF instance, or as achain of VNF instances.

Order decomposition includes translating business orders into a networkoriented service implementation plan. For example, a business order maybe decomposed into a plurality of functions, some of which may beprovided by different software programs or modules (e.g. such as variousVNFs) instantiated as a plurality of VNF instances across one or moredata centers. Performing order decomposition, the service fulfillmentmodule 435 may consult the deployment optimization module 433 for thebest deployment option to customer order in a given network and resourcecondition. Performing order decomposition, the service fulfillmentmodule 435 may then initiate the service including all its components.Order decomposition may be performed in several locations across anNFV-O hierarchy. For example, initial decomposition may be performed inthe root of the NFV-O, and then further decomposition may be performedin the relevant data centers.

In one embodiment, an activation and provisioning module may provide theplan for activation and provisioning of the service to the orchestrationand workflow management 432. The activation and provisioning module mayalso provide feedback on fulfillment status to an upper layer. Thisupper layer may include the business support services (BSS).

The NFV management system 411 may also include an assurance module 436and a service management module 452 capable of gathering real time dataon network elements' status and creating a consolidated view of servicesand network health. The assurance module 436 includes assurancefunctionality and may interact with the service management module 452 toperform assurance related lifecycle management procedures. Lifecyclemanagement can be also triggered by other modules, policies, manualintervention, or from the VNFs themselves, etc. The assurance module 436and the service management module 452 may also trigger events associatedwith lifecycle management and faults. The assurance module 436 and theservice management module 452 may monitor the health of the network andmay execute fault recovery activities.

The assurance module 436 and the service management module 452 providethe ability to monitor services' status and performance according to therequired criteria. The assurance module 436 and the service managementmodule 452 may also interact with the network infrastructure (e.g.including computing, storage, and networking, etc.) to receive therequired information, analyze the information, and act upon eachincident according to the defined policy. The assurance module 436 andthe service management module 452 are able to interact with analytics toenrich a policy assurance module. Interfaces may also be provided forimplementation by an external system.

The NFV management system 411 may also include a policy managementmodule 437 that enables a user to define and configure offline and/orreal-time policy for controlling VNF and service related rules. Thepolicy management module 437 may contain the preconfigured policies andactivities as well as selection rules for the NFV-O process to determinethe preferred policy or activity to be performed for a particularprocess event. The policy management may be multi-layered, includingvendor policy, service policy, and operator policy, etc. The policymechanism may trigger the suitable policy layer(vendor/service/operator).

The NFV management system 411 may also include an administration module438 that provides an overall view of the network, manual lifecyclemanagement and intervention, and manual system administration andconfiguration. The administration module 438 may be operable to enable auser such as an administrator (e.g. administrator 222 of FIG. 2, etc.)to manage, view, and operate the NFV-O system. The administration module438 may also provide a view of the network topology and services, theability to perform specific activities such as manual lifecyclemanagement, and changing service and connectivity configuration.

The NFV management system 411 may also include an inventory managementmodule 439 that maintains a distributed view of deployed services andhardware resources. Inventory catalogues may reflect the currentinstantiation and allocation of the resources and services within thenetwork mapped into products and/or customer entities.

The NFV management system 411 may also include a big data analyticsmodule 440 that analyzes network and service data to support networkdecisions involving services and subscribers to improve networkperformance based on actual usage patterns. The big data analyticsmodule 440 may also generate what-if scenarios to supportbusiness-oriented planning processes. Additionally, the big dataanalytics module 440 may function to analyze and evaluate theinformation for various planning aspects (e.g. Virtual Network CapacityPlanning, Data Center Capacity Planning, Value based planning, Costanalysis for network deployment alternatives, etc.), deployment andmanagement (e.g. Guided Operator Recommendations, What-if scenarioanalysis and simulation, application rapid elasticity and resource usageoptimization, etc.), and may support business-oriented planningprocesses.

The NFV management system 411 may also include a catalog module 441 mayinclude records defining various aspects of the network, such asproducts, services, and resources such as hardware units and VNFs (e.g.a VNF directory, etc.). The catalog module 441 may include a collectionof centralized, hierarchical information repositories containingresource, service and product definitions with their relationship,versioning, and/or descriptors, etc. Such records may include templatesenabling a user, such as an administrator, to define particular networkcomponents such as resources, products, services, etc. A resourcetemplate may define resources descriptors, attributes, activities,procedures, and/or connectivity, etc. A service template may define aservice variation from resource building blocks. A product template maydefine parameters of a sellable product (e.g. prices, rating, etc.)based on service composition (e.g. in one embodiment, this may be partof a BSS catalogue).

The inventory management module 439, the big data analytics module 440,and/or the catalog module 441 may support multiple data centers,multiple CMSs and provide a centralized view across the infrastructure.The inventory management module 439, the big data analytics module 440,and/or the catalog module 441 may also support hybrid networks andservices maintaining both physical and virtual resources.

The NFV management system 411 may also include an accounting andlicensing module 442 that may be operable to record and manage networksoftware usage data for commercial purposes including licensing,accounting, billing, and reconciliation of services with subscribers andproviders. The accounting and licensing module 442 may manage licensingand usage of virtual network applications, including the ability tosupport complex rating schemes, based on various parameters such as CPU,memory, data, etc. The accounting and licensing module 442 may enableusers to define the pricing of particular VNF modules and providesettlement with vendors. The accounting and licensing module 442 mayalso enable the evaluation of internal costs of services provided withinthe network for calculating return on investment (ROI).

The NFV management system 411 may also include a fault recovery module443 (otherwise named disaster recovery planning module or DRP, etc.)that enables a user to plan and manage disaster recovery procedures forthe NFV-O and/or the entire network.

The NFV management system 411 may also include a security managementmodule 444 that provides the authentication authorization and accountingservices of application security across the network. The securitymanagement module 444 may include, for example, an authentication moduleand function. In one embodiment, the authentication module and function(e.g. including identity management, etc.) may authenticate the identityof each user defined in the system. Each user may have a unique useridentity and password. The system may support password basedauthentication with flexible password policy. Integration with externalauthentication providers may be done via additional system enhancements.The authorization module and function may support a role-based accesscontrol (RBAC) mechanism, where each user is assigned with one or moreroles according to the business needs based on the least privilegesconcept (e.g. standard or administrator roles). In one embodiment, theaccounting and licensing module 442 may provide an audit of securityevents such as authentication or login events.

As an option, the security management module 444 may use rules toprotect sensitive information. For example, such rules may be used toensure the data accessed is used for the specific purposes for which itwas collected, sensitive information is encrypted when instorage/transit and masked/truncated on display and logs, and that theentire security system is deployed in the customer's intranet network(i.e. behind network/infrastructure measures), in an independent domain,etc.

In one embodiment, the NFV management system 411 may further include aSecure Development Life Cycle (SDLC) module that ensures that securityaspects are handled during a project's life cycle, such as securitydesign, security testing, etc.

As shown further in FIG. 4, the NFV management system 411 may include aservice planning module 445. The service planning module 445 may be usedby a communication service provider (CSP) sales representative,enterprise, and/or technician, as part of selling engagement processwith enterprise/SMB customers.

The service planning module 445 may also provide the ability to interactwith catalogues, customer data, network and ordering systems to provideonline network service proposals for the enterprise customers withability to quote update the proposal, validate the serviceability andnetwork inventory, and once done, provide the service order foractivation using the northbound interface.

The NFV management system 411 may also include east/west APIs 446 thatinclude various domains/activities interfaces, including an informationsource to a big data repository, and interaction capability with aphysical network system (OSS).

Northbound APIs 447 provides application programming interfaces (APIs)to various external software packages, such as business support system(BSS) for service order fulfillment, cancel and update activities,status notification, resource inventory view, monitoring system,assurance system, service planning tool, administration tool for systemview and configuration, and big data repository, etc.

Further, the southbound APIs 448 may provide APIs for external softwarepackages, such as CMS (including service and VNFs lifecycleactivities—receiving from the infrastructure status and monitoringinformation for upstream system and activities [e.g. assurance]), an SDNController (or other connectivity system) to configure inter and intradata center connectivity, an EMS to configure the VNF, and a VNF for adirect configuration.

FIG. 5 illustrates a simplified diagram 500 of a deployed NFV-basednetwork 510, in accordance with one embodiment. As an option, thediagram 500 may be viewed in the context of the details of the previousFigures. For example, in one embodiment, the deployed NFV-based network510 and associated elements may represent the NFV-based networks andassociated elements described in the context of the previous Figures. Ofcourse, however, the diagram 500 may be viewed in the context of anydesired environment. Further, the aforementioned definitions may equallyapply to the description below.

As shown in FIG. 5, the NFV-based network 510 may include hardware units523 connected via transmission lines 549, and VNFs implemented assoftware programs 550 installed in hardware units 523. Some of thehardware units 523 may be directly connected to a customer. The customermay be a subscriber, an end-user, or an organization, represented hereinas a terminal or a server 552, or a plurality of terminals and/orservers 552. The NFV-based network 510 may also include a NFV managementsystem 511 and an NFV-orchestration (NFV-O) 512 (which may all representelements described in the context of the previous figures, etc.).

As shown further in FIG. 5, several, typically different, VNFs 550 maybe installed in the same hardware unit 523. Additionally, the same VNF550 may be installed in different hardware units 523.

A VNF 550 may be executed by a processor of the hardware unit 523 in theform of a VNF instance 551. Therefore, a particular VNF 550 installed ina particular hardware unit 523 may be “incarnated” in (e.g. initiated,executed as, etc.) any number of VNF instances 551. The VNF instances551 may be independent of each other. Additionally, each VNF instance551 may serve different terminals and/or servers 552. The NFV-basednetwork 510 connects to and between communication terminal devices 552that may be operated by one or more customers, subscribers, and/orend-users.

It is appreciated that a network operator may manage one or moreservices deployed in the customer's premises. Therefore, some of thehardware units 523 may reside within the premises of the networkoperator, while other hardware units 523 may reside in the customer'spremises. Similarly, a server, such as server computer 216 of FIG. 2,may reside in the premises of the network operator or in the customer'spremises. Consequently, when the network operator provides and/ormanages one or more services for a customer's terminal devices 552 suchas a server computer, the NFV-based network 510 of the network operatormay directly manage the VNFs 550, providing the services and their VNFinstances 551.

In such situation, the NFV-based network 510 may manage the servicesirrespectively of the location of the terminal devices 552 (e.g. theserver computer 216, etc.), whether in the premises of the networkoperator or in the customer's premises. In other words, the NFV-basednetwork 510 may be managing the VNFs 550 and the VNF instances 551providing the services, as well as the terminal devices 552 (e.g. theserver computer 216, etc.) being co-located within the same computingdevice (e.g. the hardware unit 523, etc.), whether in the premises ofthe network operator or in the customer's premises or in a commercialcloud or any other place.

A service provided by the communication network may be implemented usingone or more VNFs. For example, the service may be a group, or a chain ofinterconnected VNFs. The VNFs making the group, or the service, may beinstalled and executed by a single processor, by several processors onthe same rack, within several racks in the same data-center, or byprocessors distributed within two or more data-centers. In some cases,chain optimization may be employed by optimizing the deployment of aservice in a communication network using network functionvirtualization, and to optimizing the deployment of a group, or a chain,of virtual network functions in the NFV-based network 510. Therefore,the term “chain optimization” refers to the planning and/or managing ofthe deployment of VNFs making a chain, or a group, of VNFs providing aparticular service.

For example, FIG. 5 shows a first service 553, including the VNFs 550and their respective VNF instances 554, 555, 556, and 557, and a thickline. In this example, the group or chain of the VNFs 550 making firstservice 553 are connected as a chain of VNFs 550. However, the VNFs 550making a service may be connected in any conceivable form such as astar, tree-root, tree-branch, mesh, etc., including combinationsthereof. It is noted that the VNFs 550 may be executed by two or moreVNF instances 551, such as VNF 554.

The deployment of the group or chain of the VNFs 550 making the firstservice 553 is therefore limited by constraints such as the capacity ofthe communication link 549 bandwidth and/or latency (delay).

A VNF may have a list of requirements, or specifications, such asprocessing power, cash memory capacity, regular memory capacity (e.g.RAM, dynamic, or volatile memory, etc.), non-volatile memory (e.g. suchas flash memory, etc.) capacity, storage capacity, power requirements,cooling requirements, etc. A particular VNF instance 551 providing aparticular function (e.g. to a particular customer, entity, etc.) mayhave further requirements, or modified requirements, for example,associated with a particular quality of service (QoS) or service levelagreement (SLA). Such requirements may include maximum latency or delay,average latency and maximum variance (latency jitter), maximal allowedpacket loss, etc. Other requirements may include service availability,redundancy, backup, provisions for roll-back and/or recovery,fault-tolerance, and/or fail-safe operation, etc.

A service made of a chain or a group of VNFs 550 and their VNF instances551 may have a similar list of requirements, or specifications, coveringthe service as a whole. Therefore, such requirements, or specifications,may imply, affect, or include, requirements, or specifications,regarding communication links between the VNFs 550 and/or the VNFinstances 551. Such requirements, or specifications, may includebandwidth, latency, bit-error rate, and/or packet loss, etc. Suchcommunication requirements or specifications may further imposedeployment limitations, or constraints, requiring particular VNFs 550and/or VNF instances 551 to reside in the same data-center, or withinthe same rack, or even in the same computing device, for example,sharing memory or being executed by the same processor. Securitymeasures may add further requirements, or specifications, such asco-location of some of the VNFs 550 and/or the VNF instances 551.

In the context of FIG. 5, the NFV-based network 510 has a hierarchicalstructure. There may be at least four aspects of the hierarchicalstructure of the NFV-based network 510. The networking or traffic aspectrefers to the arrangement of the transmission lines between the hardwareunits 523. The processing aspect refers to the arrangement of thehardware units 523. The software aspect refers to the arrangement of theVNFs 550. The operational aspect refers to the arrangement of the VNFinstances 551.

One aspect of the optimization process in an NFV-based network is thatit may be based on real-time needs, rather than long-term, statisticallyanticipated, needs. One potential limitation on network reconfigurationin NFV-based networks is that network configuration does not result in adeterioration beyond acceptable level of any of the current services.The NFV deployment module (e.g. module 433 of FIG. 4, etc.) may functionto enable and manage migration of services between the hardware units523, the VNFs 550, and the VNF instances 551 in real-time, withoutaffecting or with a minimal effect on the availability of a service, andwhile securing service and session continuity.

In the context of the current description, the term “continuous” meansthat the deployment optimization module and/or a chain optimizationmodule (e.g. the chain optimization module 434 of FIG. 4, etc.) performsthe relevant optimization task or process in run-time, or real-time, oronline, or on-the-fly, or repetitively and without adversely affectingthe network's functionality and its services.

Unlike a legacy network, the NFV-based network may have two topologies:the topology of the hardware devices, and the topology of the VNFs (thedistribution of VNFs among the hardware devices). The topology of thehardware network is relatively stable, while the VNF topology can beoptimized in real-time. Another benefit of the NFV-based network is thatmodifying the software topology (e.g. the distribution of VNFs among thehardware devices) is much less costly than any modification of thehardware topology. However, any modification of the network has itscost, including the cost of making such modification possible. Addedcost may result from the need to process the modification of thetopology and the re-distribution of VNF instances and to maintain excessresources for such purpose.

Thus, in some cases, it may be desired to localize the NFV-O 512, andparticularly the deployment optimization processes associated with thedeployment optimization module and the chain optimization module toreduce the cost, and simultaneously to secure the possibility to expandthe scope of the network managed by these processes, if needed.

FIGS. 2 through 5 illustrate systems and environments to which certifiedVNFs may be deployed. Currently, service providers need to invest muchtime and effort in order to onboard new VNFs from a VNF vendor.Utilizing the online automated VNF certification system and toolsdescribed herein, service providers may perform compile levelvalidation, deployment on data centers and testing, andperformance/security testing in an efficient manner. In this way, theonline automated VNF certification system may be implemented to performindustry wide VNF certification.

Service development is constrained by the speed of the NetworkEngineering create, test and debug cycle. Typically, this is a verymanual, document-based and time-consuming process. The online automatedVNF certification system addresses service development agility byoffering highly automated design of new and updated services and virtualresources, as well as automatic readiness for rapid service launch. Theonline automated VNF certification system offers an online VNFon-boarding certification portal for vendors, based on best practices,by running VNF on-boarding tests. The online automated VNF certificationsystem may be used by service providers to enforce certification as apre-requisite to procurement.

FIG. 6 illustrates a system flow diagram 600 for automaticallycertifying a VNF for use in an NFV-based communication network, inaccordance with one embodiment. As an option, the system flow diagram600 may be viewed in the context of the details of the previous figures.Of course, however, the system flow diagram 600 may be viewed in thecontext of any desired environment. Further, the aforementioneddefinitions may equally apply to the description below.

As shown, the online automated VNF certification system implements threelevels of VNF on-boarding certification. The first level ofcertification includes a compile level validation of VNF packagemetadata. For example, the first level of certification may includetesting the VNF documentation for an accurate TOSCA (Topology andOrchestration Specification for Cloud Applications) format.

The second level of certification includes a runtime validation focusingon basic deployment associated functionality associated with the VNF.The third level of certification includes a runtime validation includingconfiguration validation, life cycle management and monitoring,functional certification, a basic performance indication, securitychecks, and/or service provider specific performance tests, etc.

The second and/or the third level certification may include executingtest cases that may either come from vendors, ETSI testingdocumentation, a VNF guidelines document, and/or from test developers.The level two and three certification may also include testing based ona Network Cloud Service Orchestrator (NCSO), VNF functionalcertification, and/or vendor or service provider test cases.

With respect to the first level of certification and the manner in whichVNFs are packaged, the online automated VNF certification system mayexpect and verify that the VNF information is packaged according to adefined standard (e.g. as defined by ETSI, etc.). This standard mayspecify how vendors are to deliver VNFs to service providers. Thisenables uniform packaging and may include information associated withinstalling and/or configuring a VNF.

A VNF package may include VM (virtual machine) images and/or otherartifacts. The package may also specify VNF properties, resourcerequirements, and/or life-cycle methods, etc.

Generally, a standard VNF package is configured and deployed by aservice provider and outputs of such deployed VNF packages may include,for example, HEAT templates, configuration drives, and/or images. Theoutput may also be environment specific (e.g. VMWARE, etc.).

The VNF packaging life-cycle may include VNF package bundling fordistribution, metadata testing (e.g. level one certification),pre-procurement, installation/validation/testing (e.g. level twocertification), and software updates. The VNF package content mayinclude, for example, license information, security information,software images, package metadata (e.g. ID, name, software version,etc.), and VNF metadata (e.g. a VNF model including informationassociated with connectivity, policy, affinity, deployment, and servicelife-cycle management, etc.).

FIG. 7 illustrates a system flow diagram 700 for automaticallycertifying a VNF for use in an NFV-based communication network, inaccordance with one embodiment. As an option, the system flow diagram700 may be viewed in the context of the details of the previous figures.Of course, however, the system flow diagram 700 may be viewed in thecontext of any desired environment. Further, the aforementioneddefinitions may equally apply to the description below.

In operation, and in accordance with one embodiment, a VNF vendor mayreceive a “questionnaire” (e.g. according to a VNF packaging ETSIstandard, etc.). The vendor may answer the questions and provide therequired data to a service design and creation (SD&C) sub-systemassociated with an online automated VNF certification system. The vendormay provide information such as a VNF image and deployment scripts, aVNF descriptor, etc., as part of a VNF package (see step 1).

In one embodiment, a VNF designer may enter this data into the onlineautomated VNF certification system utilizing an SD&C onboarding userinterface, referred to as a service provider portal in FIG. 7 (see step2). In another embodiment, the online automated VNF certification systemmay automatically parse and enter the received information. The onlineautomated VNF certification system then automatically performs a levelone certification by verifying a format and structure of the providedinformation, as well as VNF descriptor integrity. Other artifacts mayalso be validated and admitted as conforming to certain standards (e.g.an ETSI standard).

A VNF designer may then model the VNF utilizing the SD&C user interface.The designer may then instantiate the VNF. In one embodiment, the onlineautomated VNF certification system may automatically configure and/ormodel the VNF and then instantiate the VNF. The SD&C may generate theartifacts associated with the VNF or use those provided by a VNF vendoras part of a VNF package.

The online automated VNF certification system then performs a level twocertification on the VNF. This may include testing artifact production(e.g. HEAT, etc.), software image distribution, and/or policyconfiguration.

In one embodiment, level two certification may include validatingcommunication with VNF VM(s), the artifacts production (e.g., HEAT,YANG, etc.), software image distribution, policy configuration, andcommunication with the VNF via YANG, etc.

The online automated VNF certification system then performs a levelthree certification of the VNF, which may include executing a pluralityof test cases for testing the functionality of the VNF. This mayinclude, for example, testing the end-to-end network service deployment,simulating the data traffic in order to enforce scale-in/out procedure,and testing VNF monitoring capabilities and policy decisions.

The output of the SD&C sub-system is a certified VNF that is ready fordeployment into an NFV-based system. Thus, the online automated VNFcertification system offers the ability to perform VNF certification andfacilitates rapid deployment of new services.

FIG. 8 illustrates a network architecture 800, in accordance with onepossible embodiment. As shown, at least one network 802 is provided. Inthe context of the present network architecture 800, the network 802 maytake any form including, but not limited to a telecommunicationsnetwork, a local area network (LAN), a wireless network, a wide areanetwork (WAN) such as the Internet, peer-to-peer network, cable network,etc. While only one network is shown, it should be understood that twoor more similar or different networks 802 may be provided.

Coupled to the network 802 is a plurality of devices. For example, aserver computer 804 and an end user computer 806 may be coupled to thenetwork 802 for communication purposes. Such end user computer 806 mayinclude a desktop computer, lap-top computer, and/or any other type oflogic. Still yet, various other devices may be coupled to the network802 including a personal digital assistant (PDA) device 808, a mobilephone device 810, a television 812, etc.

FIG. 9 illustrates an exemplary system 900, in accordance with oneembodiment. As an option, the system 900 may be implemented in thecontext of any of the devices of the network architecture 800 of FIG. 8.Of course, the system 900 may be implemented in any desired environment.

As shown, a system 900 is provided including at least one centralprocessor 901 which is connected to a communication bus 902. The system900 also includes main memory 904 [e.g. random access memory (RAM),etc.]. The system 900 also includes a graphics processor 906 and adisplay 908.

The system 900 may also include a secondary storage 910. The secondarystorage 910 includes, for example, a hard disk drive and/or a removablestorage drive, representing a floppy disk drive, a magnetic tape drive,a compact disk drive, etc. The removable storage drive reads from and/orwrites to a removable storage unit in a well-known manner.

Computer programs, or computer control logic algorithms, may be storedin the main memory 904, the secondary storage 910, and/or any othermemory, for that matter. Such computer programs, when executed, enablethe system 900 to perform various functions (as set forth above, forexample). Memory 904, storage 910 and/or any other storage are possibleexamples of tangible computer-readable media.

As used here, a “computer-readable medium” includes one or more of anysuitable media for storing the executable instructions of a computerprogram such that the instruction execution machine, system, apparatus,or device may read (or fetch) the instructions from the computerreadable medium and execute the instructions for carrying out thedescribed methods. Suitable storage formats include one or more of anelectronic, magnetic, optical, and electromagnetic format. Anon-exhaustive list of conventional exemplary computer readable mediumincludes: a portable computer diskette; a RAM; a ROM; an erasableprogrammable read only memory (EPROM or flash memory); optical storagedevices, including a portable compact disc (CD), a portable digitalvideo disc (DVD), a high definition DVD (HD-DVD™), a BLU-RAY disc; andthe like.

It should be understood that the arrangement of components illustratedin the Figures described are exemplary and that other arrangements arepossible. It should also be understood that the various systemcomponents (and means) defined by the claims, described below, andillustrated in the various block diagrams represent logical componentsin some systems configured according to the subject matter disclosedherein.

For example, one or more of these system components (and means) may berealized, in whole or in part, by at least some of the componentsillustrated in the arrangements illustrated in the described Figures. Inaddition, while at least one of these components are implemented atleast partially as an electronic hardware component, and thereforeconstitutes a machine, the other components may be implemented insoftware that when included in an execution environment constitutes amachine, hardware, or a combination of software and hardware.

More particularly, at least one component defined by the claims isimplemented at least partially as an electronic hardware component, suchas an instruction execution machine (e.g., a processor-based orprocessor-containing machine) and/or as specialized circuits orcircuitry (e.g., discreet logic gates interconnected to perform aspecialized function). Other components may be implemented in software,hardware, or a combination of software and hardware. Moreover, some orall of these other components may be combined, some may be omittedaltogether, and additional components may be added while still achievingthe functionality described herein. Thus, the subject matter describedherein may be embodied in many different variations, and all suchvariations are contemplated to be within the scope of what is claimed.

In the description above, the subject matter is described with referenceto acts and symbolic representations of operations that are performed byone or more devices, unless indicated otherwise. As such, it will beunderstood that such acts and operations, which are at times referred toas being computer-executed, include the manipulation by the processor ofdata in a structured form. This manipulation transforms the data ormaintains it at locations in the memory system of the computer, whichreconfigures or otherwise alters the operation of the device in a mannerwell understood by those skilled in the art. The data is maintained atphysical locations of the memory as data structures that have particularproperties defined by the format of the data. However, while the subjectmatter is being described in the foregoing context, it is not meant tobe limiting as those of skill in the art will appreciate that several ofthe acts and operations described hereinafter may also be implemented inhardware.

To facilitate an understanding of the subject matter described herein,many aspects are described in terms of sequences of actions. At leastone of these aspects defined by the claims is performed by an electronichardware component. For example, it will be recognized that the variousactions may be performed by specialized circuits or circuitry, byprogram instructions being executed by one or more processors, or by acombination of both. The description herein of any sequence of actionsis not intended to imply that the specific order described forperforming that sequence must be followed. All methods described hereinmay be performed in any suitable order unless otherwise indicated hereinor otherwise clearly contradicted by context

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the subject matter (particularly in the context ofthe following claims) are to be construed to cover both the singular andthe plural, unless otherwise indicated herein or clearly contradicted bycontext. Recitation of ranges of values herein are merely intended toserve as a shorthand method of referring individually to each separatevalue falling within the range, unless otherwise indicated herein, andeach separate value is incorporated into the specification as if it wereindividually recited herein. Furthermore, the foregoing description isfor the purpose of illustration only, and not for the purpose oflimitation, as the scope of protection sought is defined by the claimsas set forth hereinafter together with any equivalents thereof entitledto. The use of any and all examples, or exemplary language (e.g., “suchas”) provided herein, is intended merely to better illustrate thesubject matter and does not pose a limitation on the scope of thesubject matter unless otherwise claimed. The use of the term “based on”and other like phrases indicating a condition for bringing about aresult, both in the claims and in the written description, is notintended to foreclose any other conditions that bring about that result.No language in the specification should be construed as indicating anynon-claimed element as essential to the practice of the invention asclaimed.

The embodiments described herein included the one or more modes known tothe inventor for carrying out the claimed subject matter. Of course,variations of those embodiments will become apparent to those ofordinary skill in the art upon reading the foregoing description. Theinventor expects skilled artisans to employ such variations asappropriate, and the inventor intends for the claimed subject matter tobe practiced otherwise than as specifically described herein.Accordingly, this claimed subject matter includes all modifications andequivalents of the subject matter recited in the claims appended heretoas permitted by applicable law. Moreover, any combination of theabove-described elements in all possible variations thereof isencompassed unless otherwise indicated herein or otherwise clearlycontradicted by context.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. A method, comprising: receiving, by a virtualnetwork function (VNF) certification system, information describing avirtual network function (VNF) capable of being implemented in a networkfunction virtualization (NFV)-based network, the information usable tomodel the VNF; performing, by the VNF certification system, a firstlevel of certification for the VNF including compile level validating ofa format and structure of the information describing the VNF; responsiveto the validation of the format and structure of the informationdescribing the VNF in the first level of certification for the VNF,modeling, by the VNF certification system, the VNF to form aninstantiated model of the VNF; performing, by the VNF certificationsystem, a second level of certification for the VNF including validatingdeployment based functionality of the VNF using the instantiated modelof the VNF, the deployment based functionality including artifactproduction associated with the VNF and software image distributionassociated with the VNF; performing, by the VNF certification system, athird level of certification including validating the VNF based on oneor more key performance indicators (KPIs); and responsive to performingthe first, second, and third levels of certification, certifying, by theVNF certification system, the VNF to indicate that the VNF is authorizedfor use thereof in the NFV-based network.
 2. The method of claim 1,wherein the one or more KPIs include one or more non-functional KPIs. 3.The method of claim 1, wherein the one or more KPIs are associated withmicro-service design.
 4. The method of claim 1, wherein the one or moreKPIs are associated with VNF design.
 5. The method of claim 1, whereinthe one or more KPIs are independent of a specific network functionvirtualization infrastructure type.
 6. The method of claim 1, whereinthe one or more KPIs are associated with resiliency.
 7. The method ofclaim 1, wherein the one or more KPIs are associated with granularscalability.
 8. The method of claim 1, wherein the one or more KPIs areassociated with license models.
 9. The method of claim 1, wherein theone or more KPIs are associated with security features.
 10. The methodof claim 1, wherein the one or more KPIs are associated with associatedwith leveraging acceleration ability.
 11. The method of claim 1,wherein: a first failure is reported when the first level ofcertification fails, a second failure is reported when the second levelof certification fails, and a third failure is reported when the thirdlevel of certification fails.
 12. The method of claim 1, wherein thethird level of certification is performed by executing one or more testcases associated with the VNF and validating results of executing theone or more test cases, wherein the one or more test cases areconfigured for testing an end-to-end network service deployment,simulating data traffic in order to enforce scale-in and scale-outprocedure, and testing VNF monitoring capabilities and policy decisions.13. The method of claim 1, wherein the information describing the VNF isincluded in package metadata defined for the VNF, and wherein the firstlevel of certification for the VNF includes compile level validating ofa format and structure of the package metadata defined for the VNF. 14.The method of claim 13, wherein the first level of certification for theVNF includes verifying that the information is packaged according to adefined standard.
 15. The method of claim 14, wherein the informationincludes virtual machine images, and wherein the information specifiesproperties of the VNF, resource requirements, and life-cycle methods.16. The method of claim 1, wherein the second level of certification isa runtime validation for the VNF.
 17. A computer program productembodied on a non-transitory computer readable medium, comprisingcomputer code for: receiving, by a virtual network function (VNF)certification system, information describing a virtual network function(VNF) capable of being implemented in a network function virtualization(NFV)-based network, the information usable to model the VNF;performing, by the VNF certification system, a first level ofcertification for the VNF including compile level validating of a formatand structure of the information describing the VNF; responsive to thevalidation of the format and structure of the information describing theVNF in the first level of certification for the VNF, modeling, by theVNF certification system, the VNF to form an instantiated model of theVNF; performing, by the VNF certification system, a second level ofcertification for the VNF including validating deployment basedfunctionality of the VNF using the instantiated model of the VNF, thedeployment based functionality including artifact production associatedwith the VNF and software image distribution associated with the VNF;performing, by the VNF certification system, a third level ofcertification including validating the VNF based on one or more keyperformance indicators (KPIs); and responsive to performing the first,second, and third levels of certification, certifying, by the VNFcertification system, the VNF to indicate that the VNF is authorized foruse thereof in the NFV-based network.
 18. A virtual network function(VNF) certification system, comprising: a memory storing computerinstructions; and a hardware processor that executes the computerinstructions to perform a method comprising: receiving informationdescribing a virtual network function (VNF) capable of being implementedin a network function virtualization (NFV)-based network, theinformation usable to model the VNF; performing a first level ofcertification for the VNF including compile level validating of a formatand structure of the information describing the VNF; responsive to thevalidation of the format and structure of the information describing theVNF in the first level of certification for the VNF, modeling the VNF toform an instantiated model of the VNF; performing a second level ofcertification for the VNF including validating deployment basedfunctionality of the VNF using the instantiated model of the VNF, thedeployment based functionality including artifact production associatedwith the VNF and software image distribution associated with the VNF;performing a third level of certification including validating the VNFbased on one or more key performance indicators (KPIs); and responsiveto performing the first, second, and third levels of certification,certifying the VNF to indicate that the VNF is authorized for usethereof in the NFV-based network.